Gold Medal Software 4/Gold Medal Software - Volume 4 (Gold Medal) (1994).iso/netutils/brir110e.arj/DOC.ZIP/INTRO.TXT

Text File | 1994-06-29 | 115KB | 2,661 lines

              BrightWorks Version 1.1
              Copyright 1994 by McAfee, Inc.
               All Rights Reserved.





Copyright 1994 by McAfee, Inc. All rights reserved. McAfee is a
registered trademark of McAfee, Inc. BrightWorks, SiteMeter,
LAN Inventory, NetShield, NetRemote, and LAN Support Center
are trademarks of McAfee, Inc. All other products or
services mentioned in this document are identified by the trademarks
or service marks of their respective companies or organizations.


McAfee, Inc.
2710 Walsh Avenue
Santa Clara, CA  95051-0963
U.S.A.

Technical Support Information
-----------------------------

Phone           [phone]
FAX             [phone]
Hours           9 a.m. to 7 p.m. EST

McAfee BBS      [phone]
        1200 bps to 14,400 bps
        8 bits, no parity, 1 stop bit
        24 hours, 365 days a year

Compuserve      GO MCAFEE

Internet        [e-mail]

If you are not a customer located in the U.S. or Canada, you can
contact a McAfee authorized agent. Agents are located in more than
50 countries aroudn the world and provide local sales and support
for our software. Please refer to the AGENTS.TXT file for a complete
list of McAfee agents.



BrightWorks consists of three major functional components:

o  Software Metering
o  Inventory Collection and Auditing
o  Software Distribution


If you purchased...             Then refer to...
BrightWorks                     Intro.txt for an introduction to BrightWorks,
                installation instructions, console usage
                instructions, and tutorials

                Metering.txt for complete usage instructions
                for the metering capability

                Inventry.txt for complete usage instructions
                for the inventory capability

                Distrib.txt for complete usage instructions
                for the software distribution capability

                Crystal.txt for complete usage instructions on
                Crystal Reports

                Ref.txt for error messages and other
                reference information

SiteMeter                       Chapter 2 of Intro.txt for installation
                instructions

                Chapter 3 of Intro.txt for console usage
                instructions

                Chapter 4 of Intro.txt for tutorial

                Metering.txt for complete usage instructions

                Crystal.txt for complete usage instructions on
                Crystal Reports

                Ref.txt for error messages and other
                reference information

LAN Inventory                   Chapter 2 of Intro.txt for installation
                instructions

                Chapter 3 of Intro.txt for console usage
                instructions

                Chapter 4 of Intro.txt for tutorial

                Inventry.txt for complete usage instructions

                Crystal.txt for complete usage instructions
                on Crystal Reports

                Ref.txt for error messages and other
                reference materials


List of Topics
1.0 Introduction
1.1 About BrightWorks
1.1 The Problem
1.1.2 The McAfee Solution
1.2 BrightWorks' Features
1.2.1 Software Metering
1.2.2 Asset Management
1.2.3 Software Distribution
1.3 BrightWorks' Economic Benefits
1.4 BrightWorks' Major Capabilities
1.5 Environment
1.6 SMRPROXY.NLM Requirements
1.7 How This Manual Is Organized
2.0 BrightWorks Installation
2.1 Before Installation
2.1.1 Determining Version Numbers
2.2 BrightWorks Installation Instructions
2.3 Basic Install
2.4 Custom Install
2.5 Upgrade Procedures
2.6 Installing NLMs
2.7 Troubleshooting
3.0 Getting Started
3.1 Introduction
3.2 The BrightWorks Console
3.2.1 Windows Terms
3.2.2 Accessing BrightWorks
3.2.3 Exiting BrightWorks
3.2.4 BrightWorks Menu Bar
3.2.5 BrightWorks Tool Bar
3.2.6 Using the Keyboard
3.2.7 BrightWorks' Help Facility
3.2.8 The .INI File
3.3 Printer Setup and Administration
3.4 Error Handling
4.0 Tutorials
4.1 Metering Tutorial
4.1.1 Creating a Metered Application
4.1.2 Viewing Application Usage
4.1.3 Creating an Authorized File
4.1.4 Specifying the File Scan Interval
4.2 Inventory Tutorial
4.2.1 Collecting Inventory Data
4.2.2 Configuring the Audit Parameters
4.2.3 Running the Audit
4.2.4 Viewing Audit Results
4.3 Distribution Tutorial
4.3.1 Creating and Compiling a Script
4.3.2 Creating a Scope
4.3.3 Scheduling a Package
4.3.4 Running the Update Program

1.0 Introduction

Welcome to BrightWorks, the easy-to-use, integrated software management
solution from the network utilities experts.

BrightWorks is a member of McAfee's family of intuitive LAN support tools,
a group of network applications all designed to reduce the cost of LAN
ownership.

NOTE:  This chapter pertains to BrightWorks, SiteMeter and LAN Inventory.


1.1 About BrightWorks

BrightWorks empowers network administrators with the tools necessary to
manage network software effectively.  By offering software metering, asset
management and software distribution capabilities, BrightWorks increases
the effectiveness of your LAN support efforts.

BrightWorks' modular design enables network administrators to structure the
solution that best fits their network management needs.  In addition to
offering three integrated functions, BrightWorks also allows access to other
McAfee management solutions.  And BrightWorks' open framework facilitates
integration with many management systems and products.

McAfee has the networking experience to deliver an integrated solution
as comprehensive and valuable as BrightWorks.

NOTE:  This manual accompanies BrightWorks, SiteMeter and LAN Inventory
products.  Refer to the chart below to determine which chapters in this
manual apply to your purchase.


CAPABILITY      AVAILABLE IN...                 CHAPTERS
Metering        BrightWorks & SiteMeter         1-11
Inventory       BrightWorks & LAN Inventory     1-4 & 12-18
Distribution    BrightWorks                     1-4 & 19-25


1.1 The Problem

As LAN technology expands, networks grow rapidly and users demand additional
capabilities. With this growth comes expanded network software support
issues. Software license compliance, driver updates, software upgrades,
hardware purchases, and network security are but a few of the network
software issues in question.  Dealing with all of these issues dramatically
increases the network administrator's workload.  Unfortunately, even as
networks grow and the number of users continues to expand, the number of
skilled network administrators typically remains constant.

In addressing these issues, network administrators are raising questions
such as:

o  How do I keep network support from becoming an overwhelming task?
o  How do I make changes to files on large numbers of workstations quickly
and without downtime?
o  How can I maintain crucial network security as the network continues
to expand?

Clearly, for network administrators, intelligent network software management
is mission critical!

1.1.2 The McAfee Solution

The solution to these problems is BrightWorks!  By offering integrated
software management capabilities for networks, BrightWorks performs:

o  Software usage tracking and license enforcement
o  Asset inventory of hardware, software, and system configuration files
o  Software and data distribution
o  Software security
o  Management reporting

With these software management tools, network administrators can maximize
resource productivity:

o  Effective allocation of resources, software and hardware, based on
actual usage
o  Increased support effectiveness enabled by active configurations
o  Accurate software purchasing based on actual usage

BrightWorks' flexibility lets you tailor network management to your specific
needs.


1.2 BrightWorks' Features

BrightWorks is packed with features that aid you in managing your network.
The following lists the features available with each of BrightWorks' main
capabilities:

1.2.1 Software Metering

o  Flexible metering methods to give you a choice between NLM and TSR-based
metering

o  Easy and simple installation of the metering methods to decrease
administrative burden

o  Option to prevent users from using local drives with an optional
2workstation TSR to help you maintain network integrity

o  Real time trustee rights granting tied to application usage (masking)
to control access to sensitive or critical network applications

o  Metering for DOS and Windows programs to ensure compliance with
software license agreements

o  Graphical display of software usage to help you make purchase decisions

o  Queue back for metered applications to ensure license compliance
and maximize the effectiveness of available resources

o  Suite metering for accurate enforcement of concurrent license agreements
for suite applications, such as Microsoft Office

o  Virus protection to prevent costly downtime due to corrupted files

1.2.2 Asset Management

o  Recording and detecting of changes in software and hardware configurations
(file servers, PCs & Macs) to eliminate the need for manual inventory

o  Inventorying for multiple sites to maximize resource usage

o  Alerting of changes in software and hardware configurations via cc:Mail,
MHS, e-mail and paging notification to enable timely network support and
provide an added level of security

o  Auto-learning of new software to reduce the time required to input new
applications

o  Detailed vendor and warranty data tracking to keep records up-to-date
and to inform purchase decisions

o  Inventory information import and export capabilities to preserve
compatibility with other products and databases

1.2.3 Software Distribution

o  Automated distribution of system files, data files and software
applications to eliminate "sneaker-net" for these functions

o  Flexible and powerful scripting language that allows you to customize
distribution of system files, data files and software applications

o  Ability to edit system files (e.g., CONFIG.SYS, AUTOEXEC.BAT) to enable
global replacement and workstation-specific changes without visiting
each workstation


1.3 BrightWorks' Economic Benefits

Using structured software management results in the following economic
benefits:

1.  Reduce user support costs by

o  reducing the time required to troubleshoot user and network problems
with an accurate, up-to-date hardware and software inventory,

o  minimizing potential software incompatibilities by preventing
unauthorized software from running,

o  allocating training dollars to minimize support calls with detailed
application usage reports by user, department or application, and

o  reducing downtime by pinpointing outdated equipment and drivers
quickly and easily.

2. Reduce network maintenance costs by

o  minimizing incompatibilities from non-standard configurations or tampering
users by standardizing and centrally enforcing PC software configurations,

o  eliminating the need to walk from PC to PC to update workstation software
configurations (i.e., network drivers, versions of DOS, CONFIG.SYS,
AUTOEXEC.BAT, etc.),

o  eliminating the need to walk from PC to PC to get an accurate hardware
and software inventory,

o  minimizing downtime for users with automatic detection and reporting of
changes to network hardware and software configurations,

o  minimizing theft by automatically detecting missing hardware,

o  eliminating wasted time spent trying to determine what equipment and
software requires upgrades,

o  configuring new workstations identically to others in an automated fashion
with pre-configured distribution packages, and

o  recovering quickly from individual PC hard drive disaster by automating
the distribution of a new configuration based on records of previous
distributions.


3.  Cut software and hardware purchase costs by

o  purchasing software based on actual simultaneous usage rather than on
counting the number of workstations attached to the network,

o  purchasing software upgrades based on actual simultaneous usage rather
than on the number of packages owned, and

o  using detailed management reports to allocate workstation equipment
based on actual usage (e.g., supplying a power user with a 486 and a mail
user with a 386).

4.  Enforce software license compliance by

o  ensuring compliance with corporate and SPA guidelines, and

o  proving software compliance with SPA-approved reports.


All of these benefits result in significant time and money savings!


1.4 BrightWorks' Major Capabilities

BrightWorks consists of three major functional components:

o  Software Metering
o  Inventory Collection and Auditing
o  Software Distribution

In addition to these capabilities, you can also access other McAfee
management solutions from the BrightWorks console by choosing the
appropriate tool bar button.

If you wish to access McAfee's NETremote+ from BrightWorks, choose the
Remote tool bar button and then refer to your NETremote+ manual for usage
instructions.

If you wish to access McAfee's LAN Support Center from BrightWorks, choose
the Tickets tool bar button and then refer to your LAN Support Center
manual for usage instructions.

NOTE:  Refer to Chapter 34 for instructions on enabling BrightWorks
smart-launch within NMS.


1.5 Environment

The following criteria must be met in order to run each BrightWorks
capability:

Brightworks:
o  Network Operating System: Novell NetWare 2.x, 3.x
o  Network Disk Space: 13 MB required, 25 MB recommended
o  Btrieve Database Access: server based: BTRIEVE.NLM
o  Operating System: DOS 3.3 or greater
o  User Interface: Microsoft Windows 3.1 in enhanced mode
o  Btrieve Datbase Access: server based: BREQUEST.EXE 6.1 or greater;
local based: BTRIEVE.EXE
o  CPU: 386SX or higher
o  RAM: 4 MB
o  Disk Space: 12 MB & 50K per workstation
o  Monitor: VGA or better
o  Workstation RAM: minimum of 640K
o  Workstation CPU: 386 or greater

SiteMeter:
o  Network Operating System: Novell NetWare 2.x, 3.x
o  Network Disk Space: 13 MB required, 25 MB recommended
o  Operating System: DOS 3.3 or greater
o  User Interface: Microsoft Windows 3.1 in enhanced mode
o  Btrieve Database Access: server based: BREQUEST.EXE 6.1 or greater;
local based: BTRIEVE.EXE
o  CPU: 386SX or higher
o  RAM: 2 MB
o  Disk Space: 5 MB
o  Monitor: VGA or better
o  Workstation RAM: minimum of 640K
o  Workstation CPU: 286 or greater
o  To restrict access to local drives: SWATCHER.COM TSR 5K

LAN Inventory:
o  Network Operating System: Novell NetWare 2.x, 3.x, 4.0
o Network Disk Space: 13 MB required, 25 MB recommended
o  Btrieve Database Access: server based: BTRIEVE.NLM
o  Operating System: DOS 3.3 or greater
o  User Interface: Microsoft Windows 3.1 in enhanced mode
o  Btrieve Datbase Access: server based: BREQUEST.EXE 6.1 or greater;
local based: BTRIEVE.EXE
o  CPU: 386SX or higher
o  RAM: 2 MB
o  Disk Space: 6 MB
o  Monitor: VGA or better
o  Workstation RAM: minimum of 640K
o  Workstation CPU: 386 or greater

NOTES: a -  BrightWorks operates on Novell NetWare via IPX/SPX and is
compatible with NetWare 4.0 and NMS.  Refer to Chapter 34.0 for instructions
on enabling BrightWorks smart-launch within NMS.
b -  BrightWorks includes multi-user BTRIEVE 5.10a.
c -  BrightWorks' inventory capability will work with Client Based and
Server Based Btrieve.  Server Based Btrieve is recommended for increased
performance.  When using BREQUEST, version 6.10c or greater is required.
Refer to Chapter 32.0 for more information on using BREQUEST.
d -  Verify that you are running the latest versions of the Btrieve files.
Updated Btrieve files can be found on Compuserve in the Novell Libraries
(GO NOVLIB).

1.5 SMRPROXY Requirements

This section describes the requirements for the SMRPROXY.NLM.

Requirements for NetWare v. 3.11 fileserver:

The new SMRPROXY.NLM which ships with SiteMeter v. 4.2 (and BrightWorks v.
1.1) is 'LSL based'. That means that to successfully run the SMRPROXY.NLM on
NetWare v. 3.11, you must load the LSLENH.NLM on the fileserver.  The
LSLENH.NLM requires that the PATCHMAN.NLM and the latest LAN drivers (.LAN)
be loaded on the fileserver.  The latest .LAN drivers require ETHERTSM.NLM
to be loaded on the fileserver  (ETHERTSM is loaded for Ethernet network
topologies.  If the customer has a token ring network topology then
TOKENTSM.NLM would be loaded instead of the ETHERTSM.NLM. Likewise,
FDDITSM.NLM, RXNETTSM.NLM and PCN2LTSM.NLM are available for their
respective topologies).  The ETHERTSM.NLM requires the MSM.NLM to be loaded.
Additionally, CLIB.NLM revision 3.12F or later must be loaded.
In short, the following new files are needed:
o  CLIB.NLM v. 3.12f
o  MSM.NLM v. 2.2
o  LSLENH.NLM v. 1.01
o  PATCHMAN.NLM v. 2.3
o  ETHERTSM.NLM, or TOKENTSM.NLM or RXNETTSM.NLM (this depends on the
Topology used)

All LAN drivers need to be updated (i.e. NE2000.LAN).
Here is an example AUTOEXEC.NCF file which shows which NLMs need to be
loaded :
    file server name vanwinkle
    ipx internal net cafe
    LOAD LSLENH           <--  automatically loads PATCHMAN.NLM.
    LOAD NE2000 PORT=340 INT=5     <--  automatically loads MSM.NLM and
                    [ETHER]TSM.NLM.
    bind IPX to NE2000 net=10
    set allow unencrypted passwords = on

NOTE: ETHERTSM.NLM is shown in brackets to emphasize that a different
'TSM.NLM' would be automatically loaded by NetWare for a different topology.
The topology in this example is Ethernet as indicated by the NE2000.LAN
driver which is being loaded.

CLIB.NLM v. 3.12F is available on Compuserve in a self-extracting compressed
file.  Have the customer log on to Compuserve, GO NOVLIB, LIB 4 and download
LIBUP2.EXE.  The rest of the required files are available in a
self-extracting compressed file called LANDR3.EXE which is also located on
Compuserve.  To get LANDR3.EXE, simply GO NOVFILES and then download the file.

LANDR3.EXE 233,440  05-18-94  3:13p
Use the following procedure to update the fileserver.
1.  Copy CLIB.NLM v. 3.12F into the SYS:SYSTEM directory.

2.  Copy LANDR3.EXE into the SYS:SYSTEM directory.

3.  Execute LANDR3.EXE in the SYS:SYSTEM directory.  Make sure that any
    older files are not marked 'Read Only' so they are overwritten by the
    new files.

4.  Please refer to the STATS.DOC document for further information on the new
    files and/or special conditions (this file now resides in your
    SYS:SYSTEM directory).

5.  At the fileserver Console ':' prompt, type Load Install.

6.  Select 'Edit Autoexec.ncf'.

7.  A line needs to be added prior to the load line of the LAN board (please
    see the example autoexec.ncf file above).

    The line is LOAD LSLENH.

8.  Down the server and bring the server back up.

9.  Verify that all the required files were loaded on the fileserver (do this
    by typing Modules at the fileserver console).

The following files are contained in LANDR3.EXE:
o  STATS    DOC   63446 10-06-93   3:55p
o  TOKENTSM NLM   9040 09-30-93   3:30p
o  MSM      NLM   15628 10-04-93   1:03p
o  FDDITSM  NLM   7847 07-07-93   5:07p
o  MSM31X   NLM   16483 10-04-93   1:04p
o  PATCHMAN NLM   9632 02-04-93  10:38a
o  NE2      LAN   4954 10-08-93  10:44a
o  NE2_32   LAN   5066 05-12-93   4:03p
o  NE2100   LAN   7224 09-24-93   4:25p
o  TOKEN    LAN   10125 06-07-93   1:29p
o  NE3200   LAN   13811 10-08-93  10:51a
o  LANDR3   TXT   26051 10-27-93   2:12p
o  RXNETTSM NLM   6202 01-06-93  10:04a
o  PCN2LTSM NLM   5691 01-30-93  11:32a
o  NE1000   LAN   4468 01-20-93   3:18p
o  !NVL1301 CFG   1169 03-12-92   2:28p
o  !NVL1401 CFG   986 06-10-92   4:02p
o  !NVL1501 CFG   11994 01-11-93   3:24p
o  !NVL0901 CFG   8293 10-04-90  10:42a
o  FIRMLOAD COM   1628 01-04-91   8:57a
o  @7154    ADF   2657 04-27-92   1:54p
o  XLOAD    EXE   13872 08-06-91   4:47p
o  XLOAD    DOC   3472 07-06-92  11:00a
o  LDR001   PTF   52920 11-06-91   4:55p
o  LDR001   DOC    3200 07-06-92  11:00a
o  NE2000   LAN   7356 10-08-93  10:47a
o  NE1500T  LAN   7226 09-24-93   4:25p
o  TOKENDMA LAN   10861 05-26-93   3:16p
o  ETHERTSM NLM   8841 09-28-93   2:41p
o  NTR2000  LAN   10272 09-13-93   2:23p
o  PM311IO  NLM   8384 04-13-93  11:28a
o  LSLENH3  NLM   10500 06-02-93  11:34a
o  IOSHIM   NLM   1649 06-09-93   9:50a
o  TRXNET   LAN   3075 01-07-93   1:23p
o  PCN2L    LAN   4726 01-29-93   8:45p
o  LSLENH   NLM   11641 11-16-92   8:29a
o  MONITOR  NLM   117775 10-26-92   9:21a
o  !NVL1201 CFG   7378 03-26-92   9:08a
o  NE32HUB  LAN   12266 01-27-93   9:11a
o  @7151    ADF   2346 07-26-89   5:08p
o  !NVL0701 CFG   2745 09-02-92   1:25p
41 file(s)

Requirements for NetWare v. 3.12 fileserver
The only new file required for NetWare v. 3.12 is CLIB.NLM v. 3.12F or later.

Use the following procedure to update the fileserver.

1.  Copy CLIB.NLM v. 3.12F into the SYS:SYSTEM directory.

2.  Down the fileserver and bring the fileserver back up.

3.  Verify that the new version of CLIB.NLM was loaded on the server (do
    this by typing Modules at the fileserver Console).

Requirements for NetWare v. 4.X fileserver
The requirements for NetWare v. 4.X is that the customer be running
NetWare v. 4.01 or later, 250 user version or lower, with bindery emulation.

NOTES:
a - SiteMeter operates on Novell NetWare via IPX/SPX. Refer to Appendix E
for instructions on enabling SiteMeter smart-launch within NMS.
b - SiteMeter includes multi-user BTRIEVE 5.10a.
c - Verify that you are running the latest versions of the Btrieve files.
Updated Btrieve files can be found on Compuserve in the Novell Libraries (GO
NOVLIB).


1.7 How This Manual Is Organized

The following lists the contents of each part of this manual:

o  Intro.txt: Introduction, Chapters 1-4: Background information, environment
requirements, technical support information, installation instructions,
console description, and tutorials for each capability.

o  Metering.txt: Metering, Chapters 5-11: Complete instructions for using the
metering capability.

o  Inventry.txt: Inventory, Chapters 12-18: Complete instructions for using
the inventory capability.

o  Distrib.txt: Software Distribution, Chapters 19-25: Complete instructions
for using the software distribution capability.

o  Crystal.txt: Crystal Reports, Chapters 26-28: Complete instructions for
using the Crystal Reports software included with the BrightWorks product.

o  Ref.txt: Reference, Chapters 29-34: Appendices regarding BrightWorks
error messages, BrightWorks file lists, inventory equipment database,
Brequest, Btrieve return status codes and BrightWorks' smart-launch
within NMS.



2.0 BrightWorks Installation

Chapter 1 introduced BrightWorks.  This chapter describes the installation
procedures for BrightWorks and also provides an installation
troubleshooting section.

NOTES: a - This chapter pertains to BrightWorks, SiteMeter and LAN Inventory.
b - Unzip the program files from the BBS into a directory on your local or
network drive.


2.1 Before Installation

To install BrightWorks, you must:

o  Be logged in to the network as a SUPERVISOR or equivalent
o  Run Windows 3.1 in enhanced mode
o  Have the following line in the [386Enh] section of your SYSTEM.INI file:

    network=*vnetbios, vnetware.386, vipx.386

o  Have a drive mapped to your system volume

The following file versions are recommended for BrightWorks' installation
and use:

o  IPX version 3.10
o  NETX version 3.26 or greater
o  Windows version 3.1 (enhanced mode)
o  VIPX version 1.13
o  NETWARE.DRV version 2.02
o  VNETWARE.386 version 1.06

NOTE:  If you are using ODI drivers instead of IPX, you must have the
following:
    - LSL version 2.01
    - IPXODI.COM version 2.1

The latest versions of these files can be found on Compuserve in the
Novell Libraries (GO NOVLIB). As of this writing, the current IPX, NETX,
and IPXODI are contained within the self-extracting file named DOSUP9.EXE.

The current versions of the Novell support drivers for Windows (VIPX.386,
VNETWARE.386, NETWARE.DRV, etc.) can be found in the self-extracting file
WINUP9.EXE.

NOTE:  As these drivers are updated and added to the Compuserve file, the
number within the Compuserve filename will increment.  For example, if
Novell were to release a newer IPX and add it to DOSUP9.EXE, the name would
change to DOSUP10.EXE.

2.1.1 Determining Version Numbers

You can determine the versions of the above software by using the following
methods:

o  To determine the installed version of IPX and the NETX shell, use the
Novell NVER command.

o  To determine the version and mode of Windows, run Windows and choose the
About Program Manager command from the Program Manager Help menu.

o  To determine the version of your Novell Windows support drivers, use the
Novell VERSION command. For example, type:

    VERSION VNETWARE.386 <ENTER>

o  To determine the version of your IPXODI.COM file, use the Novell VERSION
command.  For example, type:

    VERSION IPXODI.COM <ENTER>


2.2 BrightWorks Installation Instructions

This section provides the step-by-step instructions necessary to install
BrightWorks.

Use the following procedure to install BrightWorks on your network.  You can
exit the installation at any time by choosing the Exit button in the lower
right corner of the installation screen.

1.  Verify that you have a drive letter mapped to the SYS volume for the file
    server on which you are installing this product.

2.  Start Windows in enhanced mode.

3.  Choose the Run command from the Program Manager File menu.

    The Run dialog box displays.

4.  At the prompt, enter the path and drive letter where you unzipped the
    program files from the BBS and then type SETUP.

    For example, type:

    F:\BWORKS\SETUP <ENTER>

At this point a Log File is created and placed in your WINDOWS directory.
A Log File is an ASCII file listing the date, time and location of the
BrightWorks installation.

The Log File also lists any errors that occurred during installation.  If
an error that prevents completion of the installation process occurs, the
Log File displays.

Several messages may appear at this point in the installation:

a - If BrightWorks finds an existing Log File, you are asked if you wish
to overwrite the old file. If you answer NO to preserve the old Log File,
you are prompted to enter a new Log File name.  Enter the new file name,
and choose the OK button to continue.

b - If you are not running the BREQUEST.EXE or the Btrieve NLM, a message
displays informing you of the increased performance gained by using BREQUEST.
You are given the option to either abort the installation to load BREQUEST
or to continue with the installation.  Choose the Yes button to exit the
installation and load the BREQUEST.EXE and/or the Btrieve NLM, or choose
the NO button to continue with the installation. Please refer to Chapter 32
for more information about Btrieve.

NOTE:  It is highly recommended that you use BREQUEST as this will improve
the performance of data collection, auditing and reporting by at least
50% and by as much as 500%.  It also improves upgrade performances.

c - A message displays regarding the default target drive.  This message
informs you that mapped roots are not recognized by the install program.
Read the message, and choose the OK button to continue.  The Choose Server
dialog box displays.

5.  From the Choose Server dialog box, choose the file server on which you
    want to install BrightWorks, and choose the OK button.

    The Choose Server dialog box displays all the file servers to which
    you are currently attached and have a drive mapped.

    BrightWorks verifies that you have SUPERVISOR rights on the selected
    file server and also checks to see that your \WINDOWS\SYSTEM directory
    contains the appropriate files:

    o  VNETWARE.386
    o  VIPX.386
    o  NETWARE.DRV

    Refer to the section in this chapter entitled "Before Installation" for
    version information.

6.  Select one of the following install options:

    o  Basic Install - runs the install process with minimal user input;
    automatically creates the Program Manager group McAfee (if not found)
    containing the BrightWorks program and Readme file icons and the
    Crystal Reports program and the Readme file icons.

    o  Custom Install - allows you to choose whether or not to: copy all
    BrightWorks program files to the network, retrieve fresh copies of
    the BrightWorks inventory baseline file, retrieve fresh copies of
    the BrightWorks administration files, configure Windows 3.1 for
    BrightWorks, install Crystal Reports, install metering software to
    server, retrieve fresh copies of the BrightWorks executable files,
    or create the McAfee Program Manager group and its related icons.

    o  Upgrade - allows you to automatically upgrade from either
    previous McAfee metering software or LAN Inventory software to
    BrightWorks with minimal user input.

    Refer to the appropriate section in this chapter for procedures
    regarding the selected install option.


2.3 Basic Install

The Basic Install process automatically performs the following operations:

o  Copies BrightWorks files to the network
o  Installs the BrightWorks license
o  Creates the Program Manager group McAfee and icons for BrightWorks and
the Readme file


Continue with the following steps to complete the Basic Install procedure:

7.  Enter the full path name to where BrightWorks should be installed, and
    choose the OK button.

    The drive letter and full directory must coincide with the file server
    you selected earlier.  BrightWorks will create the directory if it
    does not exist.  The default drive letter is the first one found on the
    server you specified.  BWORKS is the default directory.

NOTES: a - The installation procedure allows you to specify a drive letter
that is mapped to a different server than the one you originally chose.
b - DO NOT install BrightWorks in the same directory as SiteMeter or LAN
Inventory.  If you wish to upgrade from versions prior to LAI 3.1 and
SiteMeter 4.1, follow the upgrade procedures in this chapter.

    If BrightWorks already exists in the specified directory, an option box
    displays asking whether or not you wish to overwrite this copy of
    BrightWorks.

    If you are installing over a BrightWorks 1.0 or greater or an LAI 3.1
    or greater, you will be prompted "Do you wish to overwrite your existing
    Inventory data files?" If you answer YES, you will need to collect all of
    the data again. Choosing NO preserves your data.

    As indicated in this message box, the minimum space required for
    BrightWorks is 15MB; the recommended free space is 24414K.  If you
    do not have the minimum space in the path you specified, an error message
    displays and you are prompted to select a different path.  If you have
    the minimum but not the recommended free space, you are given the option
    of continuing the install in the specified path or choosing another one
    with more space.

8.  Enter your Company Name, and choose the OK button.

    The Company Name length must be between 1 and 20 characters.

9.  Enter the full path name to SYS:\SYSTEM on your server.

    The default is to the first drive letter found on the server you
    specified.

10. If you are running NetWare 3.x, choose one of the following options to
    make changes to the AUTOEXEC.NCF file:

    o  Have BrightWorks make changes to your existing AUTOEXEC.NCF file
    and backup the old file as AUTOEXEC.BDI, or

    o  Have BrightWorks make changes to the AUTOEXEC.BDI file and
    leave your existing AUTOEXEC.NCF file alone for you to change at a
    later date. Refer to AUTOEXEC.BDI for the necessary changes.

11. If you wish to install the TSR option (SWATCHER used with SiteMeter),
    choose the Yes button.

    The default setting installs SMRPROXY into the SYS:SYSTEM directory.
    In addition, you can select the Swatcher option in this box.

    If you do not wish to use this option, choose the No button.

NOTE:  SMRPROXY is automatically installed if you are loading SiteMeter on
a 3.x file server.  If you wish to use Swatcher you must select that option.
If you are loading SiteMeter on a 2.x file server, you must select Swatcher.

12. Choose one of the following options to make the necessary changes to the
    WIN.INI file:

    o  Have BrightWorks make changes now to your existing WIN.INI file
    and backup the old file as *.BDI, or

    o  Have BrightWorks make changes later, saving needed changes as
    *BDI. Refer to WIN.BDI for the necessary changes. (BrightWorks adds
    the line "RPT=CRW.EXE^.rpt" to the WIN.INI file; you can still
    execute BrightWorks without making this change.)

13. Choose the OK button in the information box indicating that the
    installation completed.

14. Choose the OK button in the information box about the Readme file.

15. If you chose to modify the WIN.INI file in step 12, a dialog box
    displays, giving you the following options:

    o  Reboot the PC
    o  Terminate Windows and exit to DOS
    o  Restart Windows

    Select the desired option and choose the OK button.


When the installation is complete, a message displays informing you to
check the Log File and display the Readme file for additional information.
Double click on the Readme file icon to open the file.


2.4 Custom Install

If you select the Custom Install option, the Install Options dialog box
displays.  This dialog box allows you to select the installation options
to be performed.  The procedures required for the Custom Install depend on
the options selected in the Install Options dialog box.  If you choose all
the options, the procedure is identical to the Basic Install.  The options
in the dialog box are as follows:

o  Copy program files to the network - copies all BrightWorks files to
the target directory.

o  Copy fresh Inventory data files to network - copies new data files to
the network for use with the inventory capability.

o  Retrieve fresh copies of the Inventory Baseline files - copies only the
Inventory baseline files into the BWORKS program directory.  Your existing
baseline information is overwritten.

o  Retrieve fresh copies of the Inventory Administration files - copies
only the Inventory administration files into the BWORKS program directory.

o  Configure Windows 3.1 for product - makes the necessary changes to your
WIN.INI file.

o  Install Crystal Reports - installs the Crystal Reports files, used with
the reporting functions with BrightWorks' metering and inventory capabilities.

o  Install Metering software to server - installs BrightWorks' metering
capability.

o  Create Program Manager group  - creates the MCAFEE Program Manager
group and icons.

7.  Select all the desired options from the dialog box, and then choose
    the OK button.

8.  Enter the full path name to where BrightWorks should be installed, and
    choose the OK button.  (If you did not choose to copy BrightWorks files
    to the network only, skip to step 9.)

    The drive letter and full directory must coincide with the file server
    you selected earlier.  BrightWorks will create the directory if it
    does not exist.  The default drive letter is the first one found on the
    server you specified.  BWORKS is the default directory.

NOTES: a - The installation procedure allows you to specify a drive letter
that is mapped to a different server than the one you originally chose.
b - DO NOT install BrightWorks in the same directory as SiteMeter or LAN
Inventory.  If you wish to upgrade, follow the upgrade procedures in this
chapter.

    If BrightWorks already exists in the specified directory, an option box
    displays asking whether or not you wish to overwrite this copy of
    BrightWorks.

    If you are installing over a BrightWorks 1.0 or greater or a LAI 3.1 or
    greater, you will be prompted "Do you wish to overwrite your existing
    Inventory files?" If you answer YES, you will need to collect all of the data
    again. Choosing NO preserves your data.

    As indicated in this message box, the minimum space required for
    BrightWorks is 15MB; the recommended free space is 24414K.  If you do
    not have the minimum space in the path you specified, an error message
    displays and you are prompted to select a different path.  If you have
    the minimum but not the recommended free space, you are given the
    option of continuing the install in the specified path or choosing
    another one with more space.

9.  Enter your Company Name, and choose the OK button.  (If you did not
    choose to install the files, skip to step 10.)

    The Company Name length must be between 1 and 20 characters.

10. Enter the full path name to SYS:\SYSTEM on your server.  (If you did
    not choose to install the metering software, skip to step 13.)

    The default is to the first drive letter found on the server you
    specified.

11. If you are running NetWare 3.x, choose one of the following options to
    make changes to the AUTOEXEC.NCF file:

    o  Have BrightWorks make changes to your existing AUTOEXEC.NCF file
    and backup the old file as AUTOEXEC.BDI, or

    o  Have BrightWorks make changes to the AUTOEXEC.BDI file and
    leave your existing AUTOEXEC.NCF file alone for you to change at a
    later date.  Refer to AUTOEXEC.BDI for the necessary changes.


12. If you wish to install the TSR option (SWATCHER used with SiteMeter),
    choose the Yes button.

    The default setting installs SMRPROXY into the SYS:SYSTEM directory.
    In addition, you can select the Swatcher option in this box.

    If you do not wish to use this option, choose the No button.

NOTE:  SMRPROXY is automatically installed if you are loading SiteMeter on
a 3.x file server.  If you wish to use Swatcher you must select that option.
If you are loading SiteMeter on a 2.x file server, you must select Swatcher.

13. Choose one of the following options to make the necessary changes to
    the WIN.INI file.  (If you did not choose to configure Windows 3.1 for
    the product, skip to step 14.)

    o  Have BrightWorks make changes now to your existing WIN.INI file
    and backup the old file as *.BDI, or

    o  Have BrightWorks make changes later, saving needed changes as
    *BDI.  Refer to WIN.BDI for the necessary changes.  (BrightWorks
    adds the line "RPT=CRW.EXE^.rpt" to the WIN.INI file; you can
    still execute BrightWorks without making this change.)

14. Choose the OK button in the information box indicating that the
    installation completed.

15. Choose the OK button in the information box about the Readme file.

16. If you chose to modify the WIN.INI file in step 13, a dialog box
    displays giving you the following options:

    o  Reboot the PC
    o  Terminate Windows and exit to DOS
    o  Restart Windows

    Select the desired option and choose the OK button.


When installation is complete, a message displays informing you to check
the Log File and display the Readme file for additional information.
Double click on the Readme file icon to open the file.


2.5 Upgrade Procedures

The Upgrade Install offers you several options.  You either can install
BrightWorks, SiteMeter or LAN Inventory and copy the information contained
in your current versions of these products, or you can just copy the
information from existing software into the new BWORKS directory.  Your
existing database information is retained while your BrightWorks system
is upgraded.

NOTE:  Before upgrading from previous McAfee metering software or LAN
Inventory, make sure you backup all existing product files.  If you are
upgrading from SiteMeter, you can perform the Basic Install instead
of this upgrade procedure.

The Upgrade option automatically performs the following actions:

o  Copies BrightWorks files to the network
o  Creates the Program Manager group McAfee and icons for BrightWorks and
the Readme file

Continue with the following steps to complete the Upgrade Install procedure:

7.  Select an option from the Install Options dialog box.

    The dialog box gives you the following options for upgrading:
    o  Upgrade from Fusion 1.x, LAN Automatic Inventory 3.1x & SiteMeter
    4.1x
    o  Install and import LAN Inventory data and previous McAfee metering
    data
    o  Install and import LAN Inventory data only
    o  Install and import previous McAfee metering data only
    o  Import LAN Inventory data and previous McAfee metering data only
    o  Import LAN Inventory data only
    o  Import previous McAfee metering data only

NOTE: The import options are only available if you are upgrading from
versions prior to LAI 3.1 and SiteMeter 4.1.

    The import feature allows you to retain the data you have in either
    your LAN Inventory or previous McAfee metering software.  (If you have
    already installed SiteMeter, you do not need to import to retain the
    metering data.)

NOTE:  You can only select one of the import only options if you have already
installed BrightWorks on your network.  If you have not installed BrightWorks,
select one of the first three options to install and import previous data.

8.  Enter the full path name to where BrightWorks should be installed, and
    choose the OK button.

    The drive letter and full directory must coincide with the file server
    you selected earlier.  BrightWorks will create the directory if it
    does not exist.  The default drive letter is the first one found on
    the server you specified.

NOTES: a - The installation procedure allows you to specify a drive letter
that is mapped to a different server than the one you originally chose.
b - DO NOT install BrightWorks in the same directory as SiteMeter or LAN
Inventory.

    If BrightWorks already exists in the specified directory, an option
    box displays asking whether or not you wish to overwrite this copy of
    BrightWorks.

    As indicated in this message box, the minimum space required for
    BrightWorks is 15MB; the recommended free space is 24414K.  If you do
    not have the minimum space in the path you specified, an error message
    displays and you are prompted to select a different path.  If you have
    the minimum but not the recommended free space, you are given the option
    of continuing the install in the specified path or choosing another one
    with more space.

    If LAI files are detected in the specified directory, you are prompted
    to choose whether or not you want to use the new BrightWorks Software
    list.  Either choose the Yes button to use the new Software list, or
    choose the No button to convert your existing Software list.  (Note that
    converting your existing list may result in duplicate software entries.)
    We highly recommend using the new list for the most up-to-date software
    information.

    If you are installing over a version of BrightWorks 1.0 or greater or
    LAI 3.1 or greater, you will be prompted "Do you wish to overwrite your
    existing Inventory data files?" If you answer YES, you will need to
    collect the data again. Choosing NO preserves your data.

9.  Enter your Company Name, and choose the OK button.

    The Company Name length must be between 1 and 20 characters.

10. Enter the full path name to SYS:\SYSTEM on your server.

    The default is to the first drive letter found on the server you
    specified.

11. If you are running NetWare 3.x, choose one of the following options to
    make changes to the AUTOEXEC.NCF file:

    o  Have BrightWorks make changes to your existing AUTOEXEC.NCF
    file and backup the old file as AUTOEXEC.BDI, or

    o  Have BrightWorks make changes to the AUTOEXEC.BDI file and
    leave your existing AUTOEXEC.NCF file alone for you to change at a
    later date.  Refer to AUTOEXEC.BDI for the necessary changes.

12. If you wish to install the TSR option (SWATCHER used with SiteMeter),
    choose the Yes button.

    The default setting installs SMRPROXY into the SYS:SYSTEM directory.
    In addition, you can select the Swatcher option in this box.

    If you do not wish to use this option, choose the No button.

NOTE:  SMRPROXY is automatically installed if you are loading SiteMeter on
a 3.x file server.  If you wish to use Swatcher you must select that option.
If you are loading SiteMeter on a 2.x file server, you must select Swatcher.

13. At the prompt, enter the path name for the existing copy of LAN Inventory
    and choose the OK button. (If you did not choose to import LAN Inventory
    data, skip this step.)

    BrightWorks verifies that you have a previous version of LAN Inventory,
    makes a duplicate copy of the files and then converts them to the
    BrightWorks software.

14. At the prompt, enter the path name of the existing copy of metering
    software and choose the OK button.  (If you did not choose to import
    previous software metering data, skip this step.)

    BrightWorks verifies that you have a previous version of McAfee metering
    software, makes a duplicate copy of the files and then converts them
    to the BrightWorks software.

15. Choose one of the following options to make the necessary changes to
    the WIN.INI file:

    o  Have BrightWorks make changes now to your existing WIN.INI file
    and backup the old file as *.BDI, or

    o  Have BrightWorks make changes later, saving needed changes as
    *BDI.  Refer to WIN.BDI for the necessary changes.  (BrightWorks
    adds the line "RPT=CRW.EXE^.rpt" to the WIN.INI file; you can
    still execute BrightWorks without making this change.)

16. Choose the OK button in the information box indicating that the
    installation completed.

17. Choose the OK button in the information box about the Readme file.

18. If you chose to modify the WIN.INI file in step 15, a dialog box
    displays, giving you the following options:

    o  Reboot the PC
    o  Terminate Windows and exit to DOS
    o  Restart Windows

    Select the desired option and choose the OK button.


When the upgrade is complete, a message displays informing you to check the
Log File and display the Readme file for additional information.  Double
click on the Readme file icon to open the file.

NOTE:  If you have upgraded to BrightWorks from LAN Inventory v2.xx (and if
you have installed BrightWorks in your existing LAN Inventory v2.xx
directory), you must re-inventory hardware only on each workstation
(i.e., run EQUIP/MACEQUIP) before performing your initial BrightWorks audit.
For all workstations that are not re-inventoried before performing the
initial BrightWorks audit, their inventory will be removed from the baseline
and reported as "missing."  If you do not perform EQUIP prior to performing
an audit, you will lose the information on the PCs from the old database.


2.6 Installing NLMs

This quick start guide reviews the installation process and provides
importantinformation about installing the product NLMs.

WARNING: BTRIEVE Version 6.10 or later must be properly loaded to run the
BrightWorks/SiteMeter Administration program. For instructions on setting up
server based Btrieve, please see Chapter 32 in this manual. For
instructions on setting local PC based Btrieve, please see Step 3 below.

Note: Btrieve version 6.10c is located in Compuserve. Simply GO NOVLIB,
Library 7 and download BTR61.EXE (947,265 bytes, December 6, 1993).

If you get the following error message:

"BrightWorks: The Novell Brequester has not been loaded. BrightWorks database
will not be optimized. To optimize the performance of this program, load the
Btrieve.NLM on your server, the Brequest.EXE TSR on your workstation (with
argument /d:17000), and restart Windows and BrightWorks."

when starting SiteMeter/BrightWorks and to the best of your knowledge,
Btrieve has been properly loaded, please take the following steps:

If you want to run BREQUEST for server based Btrieve, this error could be
occuring because you have loaded the incorrect WBTRCALL.DLL file. Take the
following steps:

1.  Exit Windows.

2.  Change to the \BWORKS directory.

3.  Run USEBRQ.BAT.

    This program will copy the proper WBTRCALL.DLL file into the
    \BWORKS directory for BREQUEST.EXE.

4.  Copy the new WBTRCALL.DLL into your \Windows directory.

5.  Restart Windows.

6.  Run BrightWorks again.

This error may also occur if the BTRIEVE.NLM or the BSPXCOM.NLM is not be
loaded on the fileserver. Please take the following steps:

1.  At the fileserver console, type BSTOP.

    This unloads the NLMs.

2.  Type BSTART.

    This loads both BTRIEVE.NLM and BSPXCOM.NLM on the fileserver.

If you want to work with the client based BTRIEVE instead of the server
based BTRIEVE (BREQUEST.EXE), then take these steps:

1.  Run USEBTR.BAT.

    This ensures that you are running the proper WBTRCALL.DLL file for client
    based BTRIEVE.

2.  Add the following section to your WIN.INI:
    [btrieve]
    options=/p:3072/f:22/t:btr.trn/e

3.  Restart Windows.

4.  Run BrightWorks again.


2.7 Troubleshooting

If you receive any errors while installing or upgrading BrightWorks, display
the log file to view the errors and possible solutions.
The following lists the installation error messages and their explanations.

Error calling DLL function.
    This indicates that install was unable to find PROGLIB.DLL or
    NETWARE.DRV didn't load or wasn't configured in your SYSTEM.INI file.

    This could happen if the NetWare shell was not loaded before running
    Windows or if the wrong NetWare driver was loaded for Windows.
    Please refer to the installation requirements in this manual.

    Also, make sure:

    -The shells are loaded.
    -The following line is included in your SYSTEM.INI file in the
    [386Enh] section: network=*vnetbios, vnetware.386, vipx.386
    -You have Write and Modify rights to your Windows directory.

Install requires temporary storage on your hard drive, approximately 300K
bytes. There is not enough space on your XXXX.
    XXXX is the drive name specified. This message will display if the
    drive you specified does not have the space required to run the
    installation program.

Unable to copy or decompress file: FILENAME. Make sure that you have
permission to write to the designated path and that you included the drive
letter and that there is enough space on the destination disk.
    FILENAME is the file to be copied or decompressed.
    This message will display if 1) you do not have the write permission
    2) there is not enough space on the destination disk or 3) the
    volume (i.e., SYS) that the install is trying to write to does not
    exist.  Log in as supervisor or equivalent.

Install did not find a previously installed copy of XXXXXX in YYYYYY.
Choose OK to choose another path.
    XXXXXX is the name of the product which you want to upgrade.
    YYYYYY is the name of the path you gave for the install to check
    for the previously installed product.  This message will display
    if the install did not find the previously installed product which
    you want to upgrade in the path you specified.  Make sure you give
    the correct path to the install to find the previously installed
    product for upgrading.

This installation failed.  Please run the install again to be sure that
BrightWorks is installed correctly.  Choose OK to exit install and view the
install log file.
    This message will display when the installation has encountered
    severe problems and has aborted.  A log file may have
    the error message.  Use Windows Notepad utility to view this file.
    Make the required change and then run the install again.

Fatal Error: [Error#]
    Verify that you meet the BrightWorks configuration requirements and
    then contact McAfee Technical Support with the Error #.

Validate IPX/NETX versions, encountered NetWare Error #.
    The install process was unable to determine if your IPX and/or NETX
    versions meet the installation requirements.  If your environment
    meets the minimum requirements, continue with the installation.

You have not configured Windows to load VIPX.386. Please consult manual for
further information.
    The following line must be included in the SYSTEM.INI file, in the
    [386Enh] section:
        network=*vnetbios, vnetware.386, vipx.386

Install detected problems with your Configuration.  Click on OK to exit and
view log file.
    View the Log File for information to correct your configuration in
    accordance with the BrightWorks installation requirements.  Once you
    have corrected your configuration, re-run the installation process.

Unrecoverable Error
    Verify that you meet the BrightWorks configuration requirements, and
    then contact McAfee Technical Support with the Error #.



3.0 Getting Started

Chapter 2 described the BrightWorks installation and upgrade instructions.
This chapter introduces and discusses the BrightWorks application window.

NOTE:  This chapter pertains to BrightWorks, SiteMeter and LAN Inventory.


3.1 Introduction

The following chart describes the sections in this chapter:

SECTION                         DESCRIPTION
The BrightWorks Console         Provides instructions on launching the
                BrightWorks console, selecting menu bar
                items, using the tool bar as an alternative
                to the menu bar, and using BrightWorks'
                on-line help.

Printer Setup & Administration  Provides procedures for defining the global
                print settings on which you want to generate
                BrightWorks reports.

Error Handling                  Discusses how to handle errors.


3.2 The BrightWorks Console

This section describes the BrightWorks console.  In addition to instructions
for launching and exiting BrightWorks, it discusses the menu bar, tool bar,
and help facility.

3.2.1 Windows Terms

BrightWorks should be used with a mouse.  The table below briefly defines
several Windows terms regarding the use of the mouse and product windows.

Cancel Button:  Choosing the Cancel button exits the current dialog box
        without saving any changes you made in this dialog box or
        without executing a command you selected in this dialog box.

Choose:         Click the left mouse button (or use a key combination) on an
        item to initiate an action.  For example, "Choose the
        BrightWorks icon."

Click:          Press the left mouse button once.

Double click:   Press the left mouse button twice in quick succession.

Icon:           A graphic representation of an executable in Windows.

Point:          Position the mouse until the tip of the pointer on the
        screen rests on the desired item.

Scroll:         Use the scroll bars and buttons to move through a list of
        items.

Select:         Mark an item by clicking on it or by highlighting it with
        either key combinations or the mouse. For example, "Select
        the Include Path option."

NOTE:  The remainder of this manual assumes that you are familiar with
Windows.  Refer to your Microsoft Windows manual for information on the
fundamental operating conventions of the Windows environment.

3.2.2 Accessing BrightWorks

After successfully installing BrightWorks, a McAfee Program Manager group
and a BrightWorks program icon are created on your Windows desktop.

Use the following procedure to launch BrightWorks.

1.  Load Brequest.

    Either server-based or client-based Btrieve can be used with BrightWorks.
    Server-based Btrieve is strongly recommended due to its increased
    database access speed.

    Upon installation, BrightWorks is configured to run with Brequest.
    If you are running client-based Btrieve, you must run the USEBTR.BAT
    file in the Fusion program directory before launching BrightWorks.
    This batch file configures BrightWorks to run with local Btrieve.  For
    example, from within the Fusion program directory, issue the following
    command:

    USEBTR <ENTER>

2.  Run Windows, and double click on the BrightWorks program icon.

    If you are using Novell's local Btrieve, a message displays recommending
    that you use BREQUEST for increased database access speed.  This message
    will only display when BrightWorks cannot detect Brequest.  It will also
    display when BrightWorks is configured to run with client-based Btrieve
    (i.e., by running the USEBTR.BAT file).  To disable the warning message
    under all circumstances, place a checkmark in the "Disable warning
    message when Brequest isn't running" field.

   (To re-enable the warning message, the FUSION.INI file must be edited.)

    Refer to the section entitled "Consider Improving BrightWorks' Database
    Performance" in section 12.0 of this manual for more information about
    the Btrieve database.

    Choose the OK button to continue the BrightWorks program launch.  The
    BrightWorks application window displays.

    The application window consists of the following items which are
    discussed in this section:

    o  The BrightWorks Menu Bar
    o  The BrightWorks Tool Bar
    o  Access to BrightWorks' On-Line Help

3.2.3 Exiting BrightWorks

Use the following procedure to end a BrighWorks session.

1.  Choose the Exit command from the File menu.

    A dialog box displays prompting you to confirm the exit action.

2.  To save your monitor configuration, check the 'Save monitor
    configuration' option.

    Checking this option will save the configuration of any metering
    windows that are currently open in your BrightWorks application window.
    All open metering windows will be automatically restored upon starting
    your next BrightWorks session.

3.  Choose the OK button to close the BrightWorks application.


The BrightWorks menu bar consists of several menu items.  To choose a menu,
point to the menu name and click the left mouse button.  The menu displays.

3.2.4 BrightWorks Menu Bar

The general purpose of each menu item is defined below:

o  File - Lists file oriented commands, including those for configuring
global print settings and exiting BrightWorks.  For several of the File
menu commands, the command text and its associated action when selected
depend on the currently active window in the BrightWorks application window.
For example, when the List of Available Scripts window is active, the New
Script and Open Script commands are listed under the File menu.

o  Edit - Lists the standard editing commands used when creating and editing
software distribution scripts.

o  Administration - Lists sub-menus for each BrightWorks capability.  When
selected, each sub-menu displays a list of commands used for configuring and
managing the capability parameters.

o  Tools - Lists commands for viewing and managing capability-specific
information.  For example, choose the Inventory command to view and manage
the inventory collected by BrightWorks' inventory features.

o  Reports - Lists commands for accessing specific categories of BrightWorks
reports.

o  Window - Lists commands for positioning the open document windows in the
BrightWorks application window.

o  Help - Lists commands to access BrightWorks' on-line Windows hypertext
help.

NOTE:  Holding down the left mouse button over a menu command causes the
function of the command to display in the BrightWorks title bar at the top
of the BrightWorks application window.

3.2.5 BrightWorks Tool Bar

When using BrightWorks with a mouse, BrightWorks' tool bar buttons provide
an alternative for accessing the most frequently used BrightWorks functions.
Instead of choosing commands from the drop-down menus, you can choose the
tool bar buttons to perform the same tasks.  For example, to define
applications to be metered, you can either choose Define Metered Applications
from the Metering command on the Administration menu, or you can simply
choose the Metering tool bar button.  Both actions result in displaying the
Define Metered Applications dialog box.

The function of each tool bar button is described below:

o  Metering - Displays the Define Metered Applications dialog box used for
adding, modifying and deleting applications to be metered.

o  Security - Displays the Define Authorized Files dialog box used for
specifying files that are secure.

o  Monitor - Displays the View Application Usage dialog box used for
determining which applications are being used and by whom.

o  Inventory - Displays the View Inventory dialog box used for viewing and
managing the inventory of each audited workstation.

o  Distribute -  Displays the Available Packages window used for viewing,
creating and managing packages for distribution.

o  Remote - Provides access to optional McAfee NETremote+ software for
automated user support.

o  Tickets - Provides access to optional McAfee LAN Support Center software
for help desk automation.

o  Alerting - Displays the Alerting Options dialog box used for defining and
scheduling auditing alerts.

o  Reports - Displays the report generator that was last selected from the
Report menu.  For example, if the Inventory and Distribution command was
last chosen from the Reports menu, then the Choose Report dialog box will
display, enabling you to generate inventory and distribution reports.

NOTE:  Holding down the left mouse button over a tool bar button causes the
function of the button to display in the BrightWorks title bar at the top of
the BrightWorks application window.

3.2.6 Using the Keyboard

To use BrightWorks without a mouse, perform the standard Windows keyboard
actions to navigate through the program.

Each menu item on the BrightWorks menu bar has a keyboard mnemonic.  Press
the <ALT> key in combination with the keyboard mnemonic key to choose a menu
and cause the menu to drop down.  For example, press the <ALT><F> keys to
choose the File menu and display its commands.

Each command also has a keyboard mnemonic.  Once the menu is displayed
(i.e., "dropped down"), press the keyboard mnemonic of the command you want
to choose.

For example, from the File menu, press <P> to choose the Printer Setup
command.  You can also use the <up/down arrow> keys to move the highlight
to a desired command and press <ENTER> to select the command.

For detailed information on using a Windows application with the keyboard,
refer to your Windows documentation.

NOTE:  Some BrightWorks features require the use of a mouse and cannot be
accessed with the keyboard.

3.2.7 BrightWorks' Help Facility

BrightWorks' help facility provides on-line assistance for using the
BrightWorks software.  To get information quickly about a BrightWorks
feature or procedure, choose the Help Index command from the Help menu.

Choosing the Help Index command displays an index list of topics.
Choose the topic for which you require assistance.

BrightWorks' help system is written in a standard Windows hypertext format.
This means that you can jump from one topic to another by simply choosing
topic names from a list.  Several buttons display across the top of the Help
dialog box allowing you to search for topics and also to view a list of
the topics you have visited.

For detailed information on using a Windows help facility, refer to your
Windows documentation.

3.2.8 The .INI File

Upon installing the BrightWorks software, the FUSION.INI file is
created and placed in the Windows directory of the local workstation.  The
file can consist of the following sections:

o  [ShowBrequestWarning] - This section indicates the status of the Brequest
warning which displays upon launching BrightWorks when BrightWorks does not
detect the presence of the Btrieve NLM or VAP.  This section contains an
'Init=' line which indicates whether or not the warning is disabled
(i.e., 'Init=No' when warning is disabled; 'Init=Yes' when warning is
enabled).

o  The warning message can be disabled from within BrightWorks by checking
the "Disable message when Brequest isn't running" field when launching the
application.  The only way to re-enable the warning message after it has
been disabled is to edit the FUSION.INI file, and enter 'Init=Yes' in this
section.

o  [Report Preference] - This section indicates the reporting module that
will be accessed upon choosing the BrightWorks Reports tool bar button.
Choosing the Reports tool bar button accesses either the
Inventory/Distribution reports or the Metering/Security reports, depending
on the command that was last selected from the Reports menu.  For example,
the following section will be included in the FUSION.INI file if the
Inventory and Distribution command was last selected from the Reports menu:

    [Report Preference]
    Module=Inventory

o  [ShowBanner] - This section can be manually added to the INI file in
order to disable the About BrightWorks dialog box which displays upon
launching BrightWorks.  To disable the About dialog box at start-up time,
enter the following:

    [ShowBanner]
    Init=No

o  To re-enable the warning message, either delete this section or enter
'Init=Yes.'

o  [DisableExitPrompt] - This section can be manually added to the INI file
in order to disable the prompt which displays upon exiting BrightWorks.
This prompt allows you to save the configuration of any open metering
windows. To disable the exit prompt, add the following section to the
FUSION.INI file:

    [DisableExitPrompt]
    AutoSave=Yes

o  Note that an 'AutoSave=Yes' setting will inhibit the exit prompt and
save the configuration of the open metering windows.  An 'AutoSave=No'
setting will also inhibit the exit prompt but will not save the open
metering window settings.

o  [Alternate EXE] - This section can be manually added to the INI file in
order to change the applications that are launched when the BrightWorks
Remote or Tickets tool bar buttons are pressed.  For example, to run a third
party executable help desk program when the Tickets tool bar button is
chosen, add the following section to the FUSION.INI file:

    [Alternate EXE]
    ticket=3rdparty.exe

o  [downgrade] - This option lets you instruct the console to display either
only metering or only inventory functions when it displays. For only
metering functions, add the following section to the FUSION.INI file:

    [downgrade]
    module=metering

To display only inventory functions, add the following section to the
FUSION.INI file:

    [downgrade]
    module=inventory

o  To launch another program when the BrightWorks Remote tool bar button is
chosen, add the line 'remote=' to this section and indicate the alternative
application's executable file name.  In all cases, to successfully launch
another program from within Fusion, the program must be in the Windows
directory, Windows system directory, DOS path or search path.


3.3 Printer Setup and Administration

Before printing BrightWorks reports, you should review the global print
parameters to be sure they reflect the printer settings that you require.

Printer settings include:

o  Printer destination
o  Page orientation (portrait/landscape)
o  Paper size and source
o  Graphics resolution

The procedures for customizing the contents of individual BrightWorks reports
are discussed in the corresponding parts of this manual (e.g., Chapter 18
in Inventry.txt discusses "BrightWorks Inventory Reports").  This section
briefly presents the procedures for viewing and changing Windows global print
settings (e.g., target printer, paper size).

NOTE:  Please refer to your Windows manual for detailed procedures on
modifying the Windows print settings.

Use the following procedure to review and change your print settings.

1.  Choose the Printer Setup command from the File menu.

    The Print Setup dialog box displays.

NOTE:  The Orientation section of this dialog box does not appear when you
choose the Printer Setup command while the metering reports window is open.

2.  Select the printer you want to use for printing BrightWorks reports.

    The printer selected from your Windows printer control is selected as
    the default.  To use another printer, select a Specific Printer from
    the drop-down list associated with this field.

NOTE:  Choosing a specific printer does not permanently change your
printer setting.

3.  Select the desired orientation and paper parameters.

    Choose either the Portrait (long) or Landscape (wide) Orientation setting.
    Use the drop-down lists to define the Paper Size and Paper Source
    settings.

4.  To make additional changes to the selected printer configuration, choose
    the Options button.

    Additional settings include dithering and intensity control.

5.  Choose the OK button in the Print Setup dialog box to save the print
    settings.


3.4 Error Handling

If you encounter an error while using BrightWorks, a message box displays
with a description of the error.  Choosing the OK button returns you to
either the previous screen to select another choice or to the BrightWorks
application window if no other choices are available.

Chapter 29 of this manual lists and describes all BrightWorks errors.



4.0 Tutorials

Chapter 3 described using the BrightWorks console and keyboard.  This
chapter presents brief tutorials to introduce BrightWorks' metering,
inventory and software distribution capabilities.

NOTE:  This chapter pertains to BrightWorks, SiteMeter and LAN Inventory.


4.1 Metering Tutorial

This tutorial outlines the major steps in using BrightWorks to meter your
applications and file protect your network software.

The steps in this tutorial include the following:

1. Creating a Metered Application
2. Viewing Application Usage
3. Creating an Authorized File
4. Setting the File Scan Interval

NOTES: a -  BrightWorks' metering capability must be installed on your
network before beginning the tutorial.  If you have not already done so,
please refer to Chapter 2 for installation instructions.
b - The options and features mentioned in this tutorial are discussed in
detail in Metering.txt of this manual.

You will realize the following benefits by using BrightWorks' metering on
your network:

o  Ensured compliance with software license agreements--so you stay legal
o  Controlled access to sensitive network applications with real time
trustee rights granting
o  Maximized effectiveness of available resources with queue back feature
for metered applications
o  Virus protection for your files
o  Suite metering to accurately meter groups of applications
o  Security features to maintain network integrity

4.1.1 Creating a Metered Application

A metered application is a program file that is registered for metering
with BrightWorks.  To register an application for metering, you must specify
certain information about the application.

For this tutorial, we are going to meter the Windows program CLOCK.EXE. The
tutorial assumes that you are running Windows off of the network and that
therefore CLOCK.EXE is on a network drive. The tutorial assumes you have the
BrightWorks console open and that you have the SITEMETR.NLM running.

Use the following procedure to create this metered application.

1.  Choose the Metering command from the Administration menu.  From the
    sub-menu that displays, choose the Define Metered Applications command.

    The Define Metered Applications dialog box displays.  This dialog box
    displays all files currently registered with BrightWorks' metering and
    offers the following options:

    o  Add - allows you to register an application for metering.
    o  Modify - allows you to change a metered application's information.
    o  Delete - allows you to remove an application from metering.
    o  Attach to/Detach from File Servers - allows you to attach to or
    detach from different file servers while in BrightWorks.

2.  Choose the Add button.

    The Add Metered Application dialog box displays.

3.  Choose the Add button.

    The Browse for Files to Meter dialog box displays.  This is a standard
    Windows dialog box.

4.  Select the file CLOCK.EXE from your Windows directory.

    If you are running Windows from your local drive, you must select a
    different file stored on the network for this tutorial. BrightWorks does
    not meter local files.

5.  Select the Include Path option.

6.  Choose the OK button to exit this dialog box and insert the file name in
    the File(s) to Meter text box.

7.  Enter CLOCK in the Metered Application Name text box.

8.  Enter "CLOCK for Windows" in the Full Name text box.

9.  Enter "20" in the Maximum Number of Concurrent Users text box.

10. Enter "2" in the Queue Back Time text box.

    Queue Back Time is the length of time an application is held
    exclusively for a queued user after he or she has been notified of its
    availability.  This sets the queue back time to two minutes for CLOCK.EXE.

NOTE:  For this tutorial, we are not assigning a password or trustee rights
to CLOCK.EXE.

11. Choose the OK button to save this information.

    You are returned to the Define Metered Applications dialog box.

    This completes the steps for creating a metered application for the
    utility CLOCK.EXE.  Now only 20 concurrent users can use CLOCK.EXE on
    your network.

NOTE:  Refer to the section 6.3 entitled "Registering Applications for
Software Metering" for more information about creating metered applications.

12. Choose the Close button to return to the BrightWorks console.

    Continue with the next section to view application usage for this program.

4.1.2 Viewing Application Usage

Once you create metered applications, you can view their usage on your
network. Use the following procedure to view how many people are running
CLOCK.EXE.

1.  Minimize the BrightWorks console.

2.  Load SMRAGENT.EXE.

    This may already be loaded from the WIN.INI.  You can determine if this
    file is loaded by choosing the Windows Run command from the File menu and
    then searching for SMRAGENT in the BWORKS directory.

3.  From the Program Manager, choose the Clock icon.

    The clock displays on your screen.

4.  Minimize the clock window.

5.  Return to the BrightWorks console.

6.  Choose the Monitor button from the tool bar.

    The View Application Usage dialog box displays.

7.  Select the file server where CLOCK.EXE resides.

8.  Choose the OK button.

    The Application Usage window for the file server you have selected
    displays.  In the left hand side of the window, the program CLOCK.EXE
    is listed.  The bar next to it indicates how many users are
    currently using this program.

9.  Position the cursor to the end of the usage graph bar and depress the
    left mouse button.

    A pop-up menu displays.

10. Choose the View Current Users command.

    The Current Users window displays. Your login name will appear in this
    list as well as any other network users running CLOCK.EXE.

11. Exit this window to return to the application usage graph.


This completes the steps for viewing a metered application with the graphic
display.  Once you add additional metered applications, this graph will
reflect usage information for every application you meter.

NOTE:  Refer to section 8.3 entitled "Viewing Application Usage" for more
information about viewing application usage.  If you wish to remove metering
from CLOCK.EXE at this point, refer to section 6.3.5 entitled "Deleting
Metered Applications."

Continue the metering tutorial to protect files against viruses.

4.1.3 Creating an Authorized File

BrightWorks' metering protects your network against virus infection by
checking each file against a registered copy before it is run.  This process
is called File Integrity Scanning.

For this part of the tutorial, we will register the file CLOCK.EXE for file
integrity scanning.

Use the following procedure to register CLOCK.EXE for protection.

1.  Choose the Security command from the Administration menu.  From the
    sub-menu that displays, choose the Define Authorized Files command.

    The Define Authorized Files dialog box displays. From this dialog box
    you can:

    o  Add files to the Authorized Files list
    o  Reprotect files that are already authorized
    o  Delete files that have been authorized
    o  Attach to/Detach from different file servers

2.  Choose the Add button.

    The Browse for Files to Authorize dialog box displays.

3.  Select CLOCK.EXE.

4.  Choose the OK button.

    CLOCK.EXE is listed in the Currently Authorized Files list.

5.  Choose the Close button.

    CLOCK.EXE is now an authorized file.

NOTE:  Refer to section 7.2.2 entitled "Adding Authorized Files" for more
information about authorizing applications for file protection.

Continue with the next section to specify how often CLOCK.EXE should be
checked for any changes.

4.1.4 Specifying the File Scan Interval

BrightWorks' metering lets you specify how often files should be checked for
changes before they are executed.

Use the following procedure to set the File Scan Interval for the
authorized file, CLOCK.EXE.

1.  Choose the Security command from the Administration menu.  From the
    sub-menu that displays, choose the Specify File Scan Interval command.

    The Specify File Scan Interval dialog box displays.

2.  Slide the slide bar until the value underneath reads 20 minutes.

3.  Choose the OK button.

    Now CLOCK.EXE will be checked every 20 minutes for changes to protect
    your network from viruses.

NOTE:  Refer to section 7.4 entitled "Specifying the File Scan Interval" for
more information about specifying the file scan interval.  If you wish to
remove file protection from CLOCK.EXE at this point, follow the instructions
in section 7.2.4 entitled "Deleting Authorized Files."

This completes the metering tutorial.  All of the features introduced here
are described in full detail in Metering.txt of this manual.


4.2 Inventory Tutorial

This tutorial outlines the major steps in using BrightWorks to perform an
inventory and a subsequent audit of the components of your LAN.

The steps in this tutorial include the following:

1.  Collecting Inventory Data (using the EQUIP.EXE program)
2.  Configuring the Audit Parameters
3.  Running an Audit
4.  Viewing the Audit Results (audit log and inventory details)

NOTES: a - BrightWorks' inventory component must be installed on your
network before beginning the tutorial.  If you have not already done so,
please refer to Chapter 2 for installation instructions.
b - The options and features mentioned in this tutorial are discussed in
detail in Inventry.txt of this manual.

You will realize the following benefits by using BrightWorks' inventory
capability on your network:

o  Reduce the time required to troubleshoot user and network problems
with an accurate, up-to-date hardware and software inventory

o  Eliminate the need for manual inventory by automatically recording and
detecting changes in software and hardware configurations

o  Inventory multiple sites to maximize resource usage

o  Reduce the time required to input new applications with auto-learning
feature

o  Keep records up-to-date and inform purchase decisions with detailed
vendor and warranty data tracking

o  Reduce downtime by detecting outdated equipment

4.2.1 Collecting Inventory Data

EQUIP.EXE is the program used to collect the inventory data of your
networked PCs.  The program is executed at the machine on which you want
to perform the inventory.  Inventory data includes of hardware, software
and system file information.  Note that before running EQUIP you must set
up the Btrieve database.

Use the following procedure to collect a workstation's inventory data.

1.  Proceed to the PC workstation for which you want to collect inventory
    data.

2.  Make the BWORKS directory your current directory.

    Use the DOS CD command to change into the BWORKS program directory, or
    map a search drive to the BWORKS directory.

3.  Setup the Btrieve database.

    BrightWorks provides two batch files which setup the Btrieve database.
    Issue the batch file which corresponds to the method of Btrieve you are
    using.

    o  BRQ.BAT automatically issues the Btrieve setup command and loads
    Brequest.  Brequest uses 25-49KB of RAM, depending on the version
    and the command line switches used.  It is approximately 250% faster
    than the local Btrieve; it requires, however, that the NLM be loaded
    on the file server.  The BRQ.BAT file consists of the following:

     BREQUEST /D:17000

    o  BTR.BAT automatically issues the Btrieve setup command and loads
    local Btrieve.  Btrieve uses approximately 85KB of RAM, depending on
    the command line switches used.  It is much slower than Brequest.
    The BTR.BAT file consists of the following:

     BTRIEVE /P:3072 /F:22 /T:BTR.TRN /E

NOTE:  Because of the increase in speed, Brequest is recommended.

4.  Issue the EQUIP command and collect the hardware and software component
    data for the PC you are using.

    EQUIP /h /s <ENTER>

    where /h is the command line option used to specify hardware collection;
    /s is the command line option used to specify software collection.  All
    EQUIP command line options are listed in section 14.2 entitled "EQUIP
    Command Line Reference."

5.  Respond to the prompts that display the first time EQUIP is run in a
    transaction directory.

    Ignore this step if EQUIP has already been executed from the current
    directory.

    a - The first time EQUIP is run from any transaction directory, you
    are prompted to create new database files.  Answer Yes to this prompt by
    typing <Y> and pressing the <ENTER> key.  The EQUIP program will create
    the required transaction files.

    b - After the database files have been created, EQUIP then prompts you
    to enter a Site ID name.  BrightWorks uses the Site ID name to determine
    your workstation's location.

    For example, enter the file server name as the Site ID.  To do this,
    type:

    (file server name) <ENTER>

    where (file server name) is the name of your file server.

    Upon pressing <ENTER>, EQUIP gathers the hardware and software
    information from the workstation.

NOTE:  Follow Steps #1-4 for each networked PC you want to inventory, or
call an EQUIP batch file from your system login script to automate
inventorying of networked PCs.

4.2.2 Configuring the Audit Parameters

Several audit parameters must be defined before performing an audit of the
collected inventory data.  All audit configuration information is defined
from within the BrightWorks console.

The audit parameters that are defined in this step of the tutorial include:

o  Audit scope - the sites and file servers to be audited
o  Audited components - the inventory components to be audited
(e.g., hardware, software or both)

Use the following procedure to configure the audit parameters for this
tutorial.

1.  Choose the Inventory command from the Administration menu.  From the
    sub-menu that displays, choose the Scope of Audit command.

    The Scope of Audit dialog box displays, allowing you to select
    the sites and file servers to be included in the audit.

    To include a site or file server in the audit, click on the item name in
    the corresponding left list box, and then choose the Include button.  The
    item name is moved into the list box on the right.

    To remove a site or file server from the audit, click on the item name in
    the corresponding right list box, and then choose the Remove button.
    The item name is moved into the list box on the left.

2.  For this tutorial, include both the local site in the audit scope
    (i.e., the site that was created in the "Collecting Inventory
    Data" step of this tutorial) and the file server on which BrightWorks
    is installed.

NOTE: The Scope of Audit dialog box lists all file servers on the networ, but
only those file servers with BrightWorks installed can be audited, even if
the file server name is "included" in the Scope of Audit.

3.  Choose the OK button to accept the audit scope definition.

    When a file server is included in the scope definition, a Server
    dialog box displays prompting you to enter your login name and password.

4.  In the Server dialog box, enter your login name and password for the
    selected file server, and then choose the OK button.

NOTE:  You must have Supervisor rights or equivalent to include a file
server in the audit scope.

    The configuration changes are saved, and the Scope of Audit dialog boxes
    are closed.

5.  To define what to audit and when to audit, choose the Inventory command
    from the Administration menu.  From the sub-menu which displays, choose
    the Audit Parameters command.

    The Audit Parameters dialog box displays with the three sections: What
    to Audit, When to Audit, and Additional Options.

6.  For this tutorial, check the following audit parameters:

    o  What to Audit: PC Software and PC Hardware
    o  What to Audit: Fileserver Software and Fileserver Hardware
    o  When to Audit: When Requested

    Once these options are selected, choose the OK button to accept the audit parameters and close the
    dialog box.

NOTE:  Chapter 13 of this manual discusses the audit configuration procedures
in detail.

4.2.3 Running the Audit

Conducting an audit compiles the collected equipment inventory data from
your workstations and file servers and adds it to BrightWorks' baseline
inventory.  Performing an audit updates the baseline inventory file to
represent an accumulation of your most currently audited inventory
information.  The baseline inventory file provides data for various
BrightWorks inventory reports, on-screen viewing, automatic notification of
inventory changes, and the BrightWorks software distribution capability.

The audit process uses the currently defined audit parameters.  Therefore,
before you initiate an audit, you should verify that the audit parameters
are set properly.  (In the previous step of this tutorial, the audit scope
was defined to include the local BrightWorks site.)

Use the following procedure to perform an audit.

1.  Choose the Inventory command from the Administration menu. From the
    sub-menu that displays, choose the Audit command.

    A message displays informing you that the baseline inventory will be
    updated as a result of the audit.  In order to maintain only the most
    current inventory data, the baseline files are always updated by
    performing an audit.

2.  Choose the OK button to start the audit.

    The Audit in Progress dialog box displays while the audit is running.
    When the audit is complete, the Audit in Progress dialog box closes and
    the baseline is updated to reflect the new inventory data.

NOTE:  Chapter 15 of this manual discusses the audit process in detail.

4.2.4 Viewing Audit Results

As a result of performing an audit, BrightWorks' equipment and inventory
files are updated and are available for viewing.

The audit results that are viewed in this step of the tutorial include:

o  Audit log - a list of all audits with access to audit summary and
detail information
o  Inventory - a list of component data for PC/MAC workstations and
file servers


Use the following procedure to view the audit log and inventory details.

1.  To view the Audit Log, choose the Inventory command from the
    Administration menu.  From the sub-menu which displays, choose the
    View Audit Log command.

    The Audit Log dialog box displays with a list of all the audits that
    have been performed.  The Date, Time, Performed By, and Status
    information are listed for each audit.

2.  To view the summarized results of an audit, select the audit from the
    Audit Log dialog box and choose the Results button.

    The Audit Results dialog box displays and lists the summarized results
    of the selected audit.

    Choose the Close button to close the Audit Results dialog box.

NOTE:  The above audit log results dialog box can also be displayed by
double clicking on an audit in the Audit Log dialog box.

3.  To view the details of an audit, select the audit from the Audit Log
    dialog box and choose the Details button.

    An Audit Details dialog box displays which contains an itemized list of
    audited components, nodes, and system files.

    Use the scroll buttons and scroll bars to view all the information.
    Choose the Close button to close the Audit Details dialog box.

4.  To view the inventory of your PC/MAC workstations and file servers,
    choose the Inventory tool bar button.

    The Inventory dialog box displays and lists the workstations and file
    servers for each audited site.  Use the scroll buttons to view all the
    information.

5.  Double click on a workstation type entry.

    The detailed inventory data for the workstation displays in an inventory
    details dialog. Use the slide bars and arrows to view the information
    on the inventory screen.

    The table below briefly lists the detailed inventory data displayed for
    PC and MAC workstations.  A complete list of the detected equipment
    is provided in Chapter 31.

    PC WORKSTATION          MAC WORKSTATION
    Computer Information    Computer Information
    Mass Storage            Floppy Drives
    Keyboard/Display        Monitor Type
    Ports                   Slot Adapters and Drivers
    Network Adapter         Mounted Volumes
    Memory

6.  View additional component data regarding the workstation by choosing the
    Software Applications, Misc Equipment, System Files, and Notes buttons.

    The corresponding dialog boxes provide detailed information regarding the
    selected workstation.

NOTE:  You can also view the Software Applications, Miscellaneous Equipment,
and Notes associated with a file server.

    When you have finished viewing the information for the workstation,
    choose the OK button to return to the View Inventory dialog box.
    Choose the Close button to close the View Inventory dialog box.

NOTE:  Chapters 16 and 17 of this manual discuss reviewing audit results
in detail.


This completes the inventory tutorial.  All of the features introduced here
are described in full detail in Inventry.txt of this manual.


4.3 Distribution Tutorial

This tutorial outlines the major steps in using BrightWorks to distribute
software and scripts throughout your local area network.

NOTE:  BrightWorks' distribution component must be installed on your
network before beginning the tutorial.  If you have not already done so,
please refer to Chapter 2 for installation instructions.


The steps in this tutorial include the following:

1.  Creating and Compiling a Script
2.  Creating a Scope
3.  Scheduling a Package for Distribution
4.  Running the SDUPDATE.EXE Program at the Receiving Workstation

NOTE:  The options and features mentioned in this tutorial are discussed in
detail in Distrib.txt of this manual.

You will realize the following benefits by using the BrightWorks distribution
capability on your network:

o  Automate the distribution of system files, data files and software
applications to eliminate "sneaker-ware" for these functions

o  Customize the distribution of system files, data files and software
applications using a flexible and powerful scripting language

o  Edit system files (e.g., CONFIG.SYS, AUTOEXEC.BAT) to enable global
replacement and workstation-specific changes without having to visit each
workstation

4.3.1 Creating and Compiling a Script

A script is a series of commands to be executed on a remote workstation.
Scripts can be as simple as displaying a message on a remote user's monitor,
or they can be as complex as restructuring a hard drive and/or installing
and configuring software.

Use the following procedure to create a script.

1.  Choose the Scripts command from the Tools menu.

    The Scripts dialog box displays.  For each script you define, the last
    compilation date, the status and the file name will display.

2.  Choose the New button.

    The Open New Script dialog box displays prompting you to enter the name,
    file name and destination directory for the new script.

3.  Enter the new script information, and choose the OK button.

    Enter a script name (up to 80 characters). All typed characters are valid.
    The script name is used within BrightWorks for identifying the script.

    Enter a script file name which must follow the standard DOS conventions
    and can reside in any directory.  The script file name is used to contain
    the actual script commands.

NOTE:  It is recommended that .SCR be assigned as the extension for all script
file names.

    Upon choosing OK, the message "This file does not exist.  Create the
    file?" displays.  Choose the Yes button to create the script file.
    The Script editor window automatically displays so you can enter the
    script.  The script name being edited displays in the title bar of the
    script editor dialog box.

4.  Type the script commands.

    Script commands can be directly typed into the script editor dialog box.
    The script commands can also be selected from a list of commands by
    choosing the Paste Script Function command from the BrightWorks Edit
    menu or the Functions button.

    The script compiler requires one command per line.  No error checking is
    performed until the script is compiled.  Standard editing functions are
    available from the Edit menu on the BrightWorks menu bar.

    For the purpose of this tutorial, enter the following script command:

    WRITELN "HELLO WORLD!"

    The WRITELN script function is used to write a value (in this case,
    "Hello World") to the screen at the receiving workstation.

NOTE:  The commands and rules for using the scripting language are
documented in Chapter 22 of this manual, "Software Distribution Script
Language."

5.  Save the script contents by choosing the Save button in the Script
    Editor dialog box.

    The script is saved and the editor window remains open.  The saved
    script contents are stored in ASCII text format.

    Scripts must be compiled before they can be used in a package.  Continue
    with the following steps to compile the script.

6.  Choose the Compile button in the Script Editor dialog box.

    While a compile is in progress, the Compile Status dialog box displays.
    When the compile is complete, the Status field in the Compile Status
    dialog box indicates success or failure.  If the compile fails, the
    Function field indicates the first function found with invalid
    parameters.  The Statistics area indicates the total number of lines in
    the script (Lines field) and the number of errors found (Errors field).

    If you entered the script command exactly as shown in Step #5 above,
    your script should compile successfully.

7.  Choose the OK button in the Compile Status dialog box to continue.

    The Compile Status dialog box closes.

8.  Choose the Close button in the Script Editor dialog box to return to
    the Scripts dialog box.

    The script's status displays as COMPILED.  A script can be used in a
    package only after it has been compiled successfully.

9.  Choose the Close button in the Scripts window.

4.3.2 Creating a Scope

A scope is a group of workstations defined to receive a distributed package.
Any number of workstations can be included in a scope definition.

Use the following procedure to create a new scope.

1.  Choose the Scopes command from the Tools menu.

    The Scopes dialog box displays.

2.  Choose the New button.

    The New Scope dialog box displays prompting you to enter a name for
    the new scope.

3.  Enter the new scope name, and choose the OK button.

    A scope name can be up to 80 characters, and all typed characters are
    valid.  For example, enter the new scope name "TUTORIAL_SCOPE."

    Upon choosing OK, the Edit Scope dialog box displays prompting you to
    define the new scope.

    The Edit Scope dialog box consists of two lists:

    o  Nodes in SITE - the list on the left side of the dialog box
    consists of all node names that apply to the local site.  The site
    name is indicated by the SITE text in the list title. The nodes in
    this list are not included in the selected scope
    (i.e., the list to the right).

    o  Nodes included in Scope - the list on the right side of the
    dialog box consists of the nodes that are in the selected scope.

NOTE:  The Query Options section of the Edit Scope dialog box is used to
perform a query to filter the node names in the Nodes in SITE list.  This
procedure is discussed in detail in Chapter 23 of this manual.

4.  Define one node to be included in the scope.

    Use the push buttons in the center of the Edit Scope dialog box to
    define the scope members.  To define scope membership, select a node
    name from the Nodes in SITE list and choose the Include >> button.
    The selected node name moves from the left list to the Nodes Included
    in Scope list.

5.  Choose the Save button.

    The scope's membership is defined, and you are returned to the Scopes
    dialog box.

6.  Choose the Close button to close the Scopes dialog box.

4.3.3 Scheduling a Package

Software is distributed across your local area network by creating and
activating a package.  When a package is created, it is assigned a scope and
a "Start Date."  Upon reaching the start date and running the SDUPDATE.EXE
program at a workstation in the scope, an active package automatically gets
sent to the workstation.

Use the following procedure to schedule a package consisting of the scope
and script created in this tutorial.

1.  Choose the Packages command from the Tools menu, or choose the
    Distribute tool bar button.

    The Packages dialog box displays with the names and status information
    of all defined packages.

2.  Choose the New button in the Packages window.

    The New Package dialog box displays prompting you to enter a name for the
    new package.

3.  Enter the new package name, and choose the OK button.

    The package name can be up to 80 characters, and all typed characters are
    valid.

    Upon choosing OK, a New Package dialog box displays.   The name of the
    new package is indicated in the title bar of the dialog box.

4.  Select a script to be included in the package.

    Choose the down arrow button to the right of the Update Fileset and/or
    Update Script fields to display the list of existing filesets and scripts.
    From the drop-down list, select the script that was created during this
    tutorial.

NOTE:  A package must include a fileset and/or a script.

5.  Select the scope to receive the package.

    Choose the down arrow button to the right of the Update Scope field to
    display the list of existing scopes.  From the drop-down list, select the
    scope that was created during this tutorial.

NOTE:  A scope must be assigned to the package.  The scope must have at
least one member.

6.  Assign the package's Start Date.

    Enter the date on which the package is to be distributed.  Use the
    current date which appears as a default in this field.

7.  Assign the Active status to the package.

    Check the "Update active when saved" option to automatically place the
    package in an active state upon saving the package.  (An active package
    will get distributed automatically on its assigned start date.)

    If this field is not checked, an Inactive status will be assigned to
    the package.  An inactive package will not get distributed automatically
    on its assigned start date.

8.  Specify the package's update option.

    The selected Update Option instructs the software distribution update
    program how it should interact with the receiving workstation user at
    login time.

    For this tutorial, select the 'Force upgrade at next login' option to
    force the package's receipt on the user at the next login. If an error
    occurs, the distribution is halted so you can address the problem and
    reschedule the package.

9.  Specify the target path in which the fileset should be decompressed.

    Even though this package does not consist of a fileset, a default path
    must be assigned to the package.  The default path is the target path in
    which the distributed software (e.g., fileset) is to be installed or
    copied.

    For this tutorial, enter the default path as the workstation's boot root
    (i.e., choose the [BOOT_ROOT] option).

10. When all package attributes are defined, choose the Save button.

    The New Package dialog box closes, and the package is saved and
    assigned an active status.

4.3.4 Running the Update Program

The distribution update program (SDUPDATE.EXE) is a DOS-based program
which must be run from each workstation in order to receive the distributed
packages it has been sent.  Upon BrightWorks installation, the update
program is copied into the BWORKS program directory.

SDUPDATE [drive:[\path]]

in which drive and path are optional parameters.  The brackets are not typed.

Consider the following examples:

Example                 Result
SDUPDATE                SDUPDATE will look in the current directory.
SDUPDATE F:             SDUPDATE will look in the current
            directory on drive F:.
SDUPDATE F:\path        SDUPDATE will look in the directory F:\path.


Use the following procedure to run the update program and distribute the
active package.

1.  At the workstation which is to receive the distributed package,
    load the Btrieve Record Manager.

    Either Btrieve or Brequest can be used. Refer to section 12.6.3 entitled
    "Consider Improving BrightWorks' Database Performance" for more
    information about the Btrieve database.

2.  Make the BWORKS directory your current directory.

    Use the DOS CD command to change into the BWORKS program directory,
    or map a physical drive to the BWORKS directory.

3.  Execute the SDUPDATE.EXE program.

    For example, enter the following at the DOS command line:

    SDUPDATE

    Upon executing SDUPDATE, messages similar to the following will
    display at your workstation:

    Looking for packages, please wait...
    Installing package "TUTORIAL"...
    Created target path.
    Target path: C:\
    Disk space: ### bytes free
    Running Script "HELLO_WORLD"...
    HELLO WORLD!
    The script completed successfully.
    No more packages scheduled.


This completes the distribution tutorial.  All of the features introduced
here are described in full detail in Distrib.txt of this manual.